Business

Debugging Teams: Better Productivity Through Collaboration

Debugging Teams: Better Productivity Through Collaboration

  • Downloads：3157
  • Type：Epub+TxT+PDF+Mobi
  • Create Date：2021-10-13 09:53:58
  • Update Date：2025-09-07
  • Status：finish
  • Author：Brian W. Fitzpatrick
  • ISBN：1491932058
  • Environment：PC/Android/iPhone/iPad/Kindle
  • Download

Summary

In the course of their 20+-year engineering careers， authors Brian Fitzpatrick and Ben Collins-Sussman have picked up a treasure trove of wisdom and anecdotes about how successful teams work together。 Their conclusion？ Even among people who have spent decades learning the technical side of their jobs， most haven't really focused on the human component。 Learning to collaborate is just as important to success。 If you invest in the soft skills of your job， you can have a much greater impact for the same amount of effort。

The authors share their insights on how to lead a team effectively， navigate an organization， and build a healthy relationship with the users of your software。 This is valuable information from two respected software engineers whose popular series of talks--including Working with Poisonous People--has attracted hundreds of thousands of followers。

Download

Reviews

Ivan ，

Couldn't get past the first chapter。A very poor example out of the gate of Michael Jordan's 90s Bulls。 Emphasizing that it wasn't him but the team that won all those championships - true it was the team， but would the team have won without MJ？ I don't think so。 Could MJ go to a semi-competent team with Scotty Pippen tier player on his side and win？ For sure。A few pages later the authors drive the point of the most important aspects in successful teams - respect/trust/humility which directly cont Couldn't get past the first chapter。A very poor example out of the gate of Michael Jordan's 90s Bulls。 Emphasizing that it wasn't him but the team that won all those championships - true it was the team， but would the team have won without MJ？ I don't think so。 Could MJ go to a semi-competent team with Scotty Pippen tier player on his side and win？ For sure。A few pages later the authors drive the point of the most important aspects in successful teams - respect/trust/humility which directly contradict MJ's leadership style as evidenced by this article 。 How wouldn't the authors know of MJ's "toxic" way of handling his team mates living in Chicago in the 90s is beyond me。The next few pages describe an instance of the perfect team member class - always humble （no ego）， being respectful and having trust in the team。 I think the authors are missing the core idea of what the activity of computer programming is - a craft intelligent people take pride in。Instead of offering platitudes， I'd offer the only two actual characteristics of a good team member which are not tied to his performance （humility vs ego）: honesty and self-responsibility。 That's it。 。。。more

Ron ，

Great book although a bit bland。 The book has great overall principle， however I was hoping for more detailed solutions （it has after all "debugging" in the name）I was also a bit disappointed they dialed down on technical stuff to reach a bigger audience。Nevertheless， a good book if you're expectations are different Great book although a bit bland。 The book has great overall principle， however I was hoping for more detailed solutions （it has after all "debugging" in the name）I was also a bit disappointed they dialed down on technical stuff to reach a bigger audience。Nevertheless， a good book if you're expectations are different 。。。more

Ben ，

Primary theme of the book is HRT: Humility， Respect， and Trust。This book content is based on the authors' experience and anecdotes， along with summaries from a few other management books。 There are no studies cited and no quantification。 The book provides best practices with a focus on what to do rather than why or how。 No novel insights。 The software category covered is shrink wrapped （see Joel's Five Worlds）。 Primary theme of the book is HRT: Humility， Respect， and Trust。This book content is based on the authors' experience and anecdotes， along with summaries from a few other management books。 There are no studies cited and no quantification。 The book provides best practices with a focus on what to do rather than why or how。 No novel insights。 The software category covered is shrink wrapped （see Joel's Five Worlds）。 。。。more

Viktor Malyshev ，

This book about managing and troubleshooting teams。 MUST HAVE for any leader （both technical or management）。 This book is great。 It helped me to understand how teams are working， how to deal with people in a better way， how to build a better culture in the organization。 It has a lot of good examples from authors on how to deal with different situations in the work。 I love the examples and I can say I've been there and faced it。I'm pretty sure this will be a handbook for me for the next few years This book about managing and troubleshooting teams。 MUST HAVE for any leader （both technical or management）。 This book is great。 It helped me to understand how teams are working， how to deal with people in a better way， how to build a better culture in the organization。 It has a lot of good examples from authors on how to deal with different situations in the work。 I love the examples and I can say I've been there and faced it。I'm pretty sure this will be a handbook for me for the next few years or more。 。。。more

Maciej ，

Almost identical to "Team geek"。 Almost identical to "Team geek"。 。。。more

Sir。Nathan ，

Recommend this book to anyone on a software dev team & looking to intentionally start thinking about how to increase health good teamwork。

Codey Oxley ，

From the outside， it looks managerial。 But really it's a guide on how to organize your project communities， build trust with peers and users， and keep a healthy team culture。Some stuff is straight forward of you've worked at companies like Facebook or Google。 But it's always nice to have explicit call outs。I'd recommend it to anyone who is a main contributor to a project， or leads a team。 From the outside， it looks managerial。 But really it's a guide on how to organize your project communities， build trust with peers and users， and keep a healthy team culture。Some stuff is straight forward of you've worked at companies like Facebook or Google。 But it's always nice to have explicit call outs。I'd recommend it to anyone who is a main contributor to a project， or leads a team。 。。。more

Eliane ，

This books is useful for every and each team and not only for managers。

Eriky Kashivagui ，

Some good topics around teams and software engineering。 As the subjects are very broad the book is shallow in some of these topics。

Robert Zalog ，

I can’t really disagree with anything in here but similar to what other reviewers said， it’s mostly stuff you’ve probably heard about before （and I say that as a person who’s not a manager）。 It’s also fairly light on practical advice。 That being said I still appreciated it as it helped to cement some of the things I already sort of knew and I think it’ll be a great reference to come back to later on if I ever do become a manager or lead of something。

Denis Romanovsky ，

Very basic and shallow list of advices about teams and work in a big organizations。 More like a collection of blog posts。 This book may be good for beginners。 Feeling dissapointed。

Yoel Monzón ，

I really liked this book， taught me that creating software is not just about writing code and that people is more complicated than software。 Also， taught me that we can be better developers/leaders/persons if we apply humility， respect and trust in all our actions and relationships。

Jon Mann ，

Full of useful ideas and observations， without belabouring anything。 Mostly specific to software development， but could be of interest outside the field。

Ramón García ，

Great book。 Sometimes we just need to be reminded the obvious， in this industry we are just people working with other people。 Hopefully this book will make people reflect and change some behavious we assume as correct。

Stephen Grubb ，

Worth a selective reread

Diego Caxito ，

I recommend this book for engineers that is starting to lead some initiative， squad， team or project。 Some important cultural tips shared。

Helen Mary ，

Funny and transparent。 A good read for leaders and also individual contributors who could benefit from understanding team dynamics and their own contribution to it

Melike Bakır ，

Unlike ordinary development books， each page was a useful book， full of different best practices。 Each page contains suggestions that you can adapt to daily work life。 In addition， they embody the points that are tried to be explained with examples from their own lives。 In short， I found the book very useful， I recommend it。

Jules ，

I'm probably not the ideal audience for this， but I'd recommend it to those new to working in the tech industry to need to understand how engineering teams can operate and cooperate effectively。 I'm probably not the ideal audience for this， but I'd recommend it to those new to working in the tech industry to need to understand how engineering teams can operate and cooperate effectively。 。。。more

Michał Węgrzyn ，

There is something special in books written by engineers to engineers。 I like whatever this is and want more of it。

Robson Castilho ，

People are the main component of a project。 That said， it's extremely important to know how to build a solid team。 The authors cover a lot of scenarios of collaboration with people inside your team， how to lead them， how to shield them against poisonous people， how to collaborate with people from another areas of the company and with the users of your product。Highly recommended （whether you are an individual contributor， a team leader or intend to become one）。 People are the main component of a project。 That said， it's extremely important to know how to build a solid team。 The authors cover a lot of scenarios of collaboration with people inside your team， how to lead them， how to shield them against poisonous people， how to collaborate with people from another areas of the company and with the users of your product。Highly recommended （whether you are an individual contributor， a team leader or intend to become one）。 。。。more

Jacek Tomaszewski ，

Very good book for matured software engineers who are now stepping into more management-like or leadership-like roles。 （Especially the first two parts。 The last part focused on the users was IMHO a bit off-topic。）

Teresa Portela ，

This book really changed me and had me see the value in incorporating a mission statement， regardless of what team you’re on， or level in your company。 The principles in the book speak to Humility， Respect， and Trust， and how each of those is integral for building the best team。 It’s a very quick read， but I highlighted a lot of quotes from it。 Probably the best part speaks to how IT folks get thrust into management， it’s usually not a path we want to go down。 How do you traverse that？ Get this This book really changed me and had me see the value in incorporating a mission statement， regardless of what team you’re on， or level in your company。 The principles in the book speak to Humility， Respect， and Trust， and how each of those is integral for building the best team。 It’s a very quick read， but I highlighted a lot of quotes from it。 Probably the best part speaks to how IT folks get thrust into management， it’s usually not a path we want to go down。 How do you traverse that？ Get this book。 。。。more

Brad ，

This is a great book to read as a team。 It's full of easy to understand and practical advice。 This edition of the book is intended for a larger audience than just programmers but all the good examples are from programming teams。I liked the theme of HRT that's throughout the book -- Humility， Respect， and Trust。 Some of the ideas I found worth writing down。* Fail early， fail fast， fail often -- don't work in isolation or be afraid to share work in progress* Ask questions to guide other to their s This is a great book to read as a team。 It's full of easy to understand and practical advice。 This edition of the book is intended for a larger audience than just programmers but all the good examples are from programming teams。I liked the theme of HRT that's throughout the book -- Humility， Respect， and Trust。 Some of the ideas I found worth writing down。* Fail early， fail fast， fail often -- don't work in isolation or be afraid to share work in progress* Ask questions to guide other to their solutions。* A leader is always on stage， always being watched。 Remember the gears analogy。 Leaders have gears with more impact from small changes。* Focus on booting bad behavior from the team， not bad people。* Change behavior， not people。* When dealing with emotional responses or feedback， focus only on facts and details。* Treat people as adults， not children。 Don't be too harsh on rule breaking。 Learn why the rules are getting in the way。* Over-communicate。 Frequent updates。* Tech debt: Defensive work， contrasted to user-facing work that is Offensive。 Defense isn't sexy， but it needs done。 But rarely can you only play defense。* Look for opportunities to help others out and gain political capital。 Think of it as an investment portfolio -- some will pay off but not all。* Trust （in your product， team） is your most sacred resource 。。。more

Christian Daniel ，

The book has good tips and advice to become a better team member and improve the relationships between team

Tess Huelskamp ，

Quick， entertaining， and surprisingly dense book detailing what components make up successful software engineering - or really any！ - teams。 I didn't exactly learn anything new reading this book but find incredible value in this book being citable。Worth the read。 Quick， entertaining， and surprisingly dense book detailing what components make up successful software engineering - or really any！ - teams。 I didn't exactly learn anything new reading this book but find incredible value in this book being citable。Worth the read。 。。。more

Gedi௨ ，

Brief book on how to be a servant leader and lead your （mostly IT） teram with H（EA）RT！ Quick & easy to read and comprehend; yet one of the first few IT books quating the classical authors - Leo Tolstoy - big respect！

Lance Willett ，

The purpose of this book is to help people improve their collaborate with others。 The authors introduce it as “social challenges of creative collaboration。”Cool tech history note。 The authors worked on the Subversion open source project; and later at Google on Google Code。The book reads as a series of essays; it’s easy to pick up a chapter or section without going end to end。The “core traits to remember” are abbreviated “HRT” and stand for humility， respect， and trust。Hat tip: Andrés Bastidas。 R The purpose of this book is to help people improve their collaborate with others。 The authors introduce it as “social challenges of creative collaboration。”Cool tech history note。 The authors worked on the Subversion open source project; and later at Google on Google Code。The book reads as a series of essays; it’s easy to pick up a chapter or section without going end to end。The “core traits to remember” are abbreviated “HRT” and stand for humility， respect， and trust。Hat tip: Andrés Bastidas。 Read on Kindle in October 2018。 。。。more

Phil Sykes ，

Basic stuff （and no big surprises for me personally; much of it is in the curriculum at work）， but well written & engaging。

Shyue Ping Ong ，

This very short book covers a lot of commonsense stuff about how to manage teams and users。 It ultimately falls short in practical examples。

Reference

google book https://www.google.com/search?tbm=bks&q=Debugging Teams: Better Productivity Through Collaboration

hathitrust digital library https://babel.hathitrust.org/cgi/ls?q1=Debugging Teams: Better Productivity Through Collaboration&field1=ocr&a=srchls&ft=ft&lmt=ft

The British Library https://bll01.primo.exlibrisgroup.com/discovery/search?query=any,contains,Debugging Teams: Better Productivity Through Collaboration&tab=LibraryCatalog&search_scope=Not_BL_Suppress&vid=44BL_INST:BLL01&lang=en&offset=0